Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1699

reference
658-tree-1
name
1699
tree-preservation-order

undefined

658-tpo-1
uprn
address-text
point
POINT (-1.006979 50.863266)
geometry
MULTIPOLYGON (((-1.006837 50.863251,-1.006844 50.863279,-1.006863 50.863304,-1.006894 50.863324,-1.006933 50.863337,-1.006977 50.863342,-1.007021 50.863338,-1.007061 50.863326,-1.007093 50.863306,-1.007114 50.863281,-1.007121 50.863253,-1.007115 50.863226,-1.007095 50.863200,-1.007064 50.863180,-1.007025 50.863167,-1.006981 50.863162,-1.006937 50.863166,-1.006897 50.863179,-1.006865 50.863198,-1.006845 50.863223,-1.006837 50.863251)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL